Skip to content

Document property_info not loaded error#2262

Open
lacatoire wants to merge 2 commits into
api-platform:4.2from
lacatoire:doc-property-info-troubleshooting
Open

Document property_info not loaded error#2262
lacatoire wants to merge 2 commits into
api-platform:4.2from
lacatoire:doc-property-info-troubleshooting

Conversation

@lacatoire
Copy link
Copy Markdown
Contributor

Fixes #2249

Adds a troubleshooting section for the property_info service not found error that occurs when upgrading Symfony.

@soyuka
Copy link
Copy Markdown
Member

soyuka commented Mar 25, 2026

mhh but this probably means we need to fix something

soyuka added a commit to guillaumedelre/core that referenced this pull request May 16, 2026
…ration

| Q             | A
| ------------- | ---
| Branch?       | main
| Tickets       | Fix api-platform#7876
| License       | MIT
| Doc PR        | Closes api-platform/docs#2262

Drop the PropertyInfoPass compiler pass and register a self-sufficient
extractor chain directly in api.php: ReflectionExtractor always, plus
PhpDocExtractor and PhpStanExtractor under class_exists guards. Decorate
api_platform.property_info with PropertyInfoCacheExtractor over the
cache.property_info pool so metadata extraction is cached regardless of
framework.property_info being enabled.

Extractors remain tagged on property_info.* so ecosystem extractors
(e.g. Doctrine's) still flow into the composite via tagged_iterator.
soyuka added a commit to guillaumedelre/core that referenced this pull request May 16, 2026
…ration

| Q             | A
| ------------- | ---
| Branch?       | main
| Tickets       | Fix api-platform#7876
| License       | MIT
| Doc PR        | Closes api-platform/docs#2262

Drop the PropertyInfoPass compiler pass and register a self-sufficient
extractor chain directly in api.php: ReflectionExtractor always, plus
PhpDocExtractor and PhpStanExtractor under class_exists guards. Decorate
api_platform.property_info with PropertyInfoCacheExtractor over the
cache.property_info pool so metadata extraction is cached regardless of
framework.property_info being enabled.

Extractors remain tagged on property_info.* so ecosystem extractors
(e.g. Doctrine's) still flow into the composite via tagged_iterator.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document property info not loaded

2 participants